#13419: Handle cases where GitHub timeout on a job cuts off the data in a test in a Junit XML, leaving no data to use #13425
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…in a test in a Junit XML, leaving no data to use
tt-rkim
force-pushed
the
rkim/13419-timeout
branch
from
f361275 to
6ef964d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…
Ticket
#13419
Problem description
Sometimes when a GitHub job times out and GitHub cancels, the leftover data in the Junit XML gets cut off. We should prune test cases where such a thing happens.
What's changed
We skip processing test cases which have no
nameorclassname.Checklist